Update module github.com/DataDog/dd-trace-go/contrib/net/http/v2 to v2.2.3#50299
Conversation
renovate
Bot
added
changelog/no-changelog
ℹ️ Artifact update noticeFile name: pkg/dyninst/testprogs/progs/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
PRApprover will approve and merge this PR, FAQ, #dx-source-code-management 🛠️ PRApproval Status
➡️ Current phase: CI tests failed. Please fix the failing tests to continue. |
github-actions
Bot
added
the
short review
Files inventory check summaryFile checks results against ancestor f94eaedf: Results for datadog-agent_7.80.0~devel.git.764.87fc676.pipeline.113083545-1_amd64.deb:No change detected |
Static quality checks✅ Please find below the results from static quality gates 32 successful checks with minimal change (< 2 KiB)
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 00e3e09 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | -0.86 | [-3.77, +2.05] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | otlp_ingest_metrics | memory utilization | +0.55 | [+0.40, +0.71] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.38 | [+0.13, +0.63] | 1 | Logs bounds checks dashboard |
| ➖ | docker_containers_memory | memory utilization | +0.32 | [+0.23, +0.42] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | +0.32 | [+0.13, +0.51] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | +0.32 | [+0.25, +0.38] | 1 | Logs |
| ➖ | file_tree | memory utilization | +0.12 | [+0.07, +0.17] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.02 | [-0.41, +0.46] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.02 | [-0.03, +0.07] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | +0.01 | [-0.53, +0.56] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | +0.01 | [-0.19, +0.21] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.10, +0.09] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.21, +0.19] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.02 | [-0.15, +0.11] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.02 | [-0.18, +0.14] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | -0.05 | [-0.28, +0.19] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.08 | [-0.48, +0.32] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | -0.09 | [-0.14, -0.04] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_metrics | memory utilization | -0.20 | [-0.40, +0.00] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.34 | [-0.38, -0.30] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_logs | memory utilization | -0.47 | [-0.58, -0.37] | 1 | Logs |
| ➖ | docker_containers_cpu | % cpu utilization | -0.86 | [-3.77, +2.05] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | -0.94 | [-1.91, +0.03] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -1.51 | [-1.71, -1.31] | 1 | Logs |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | observed_value | links |
|---|---|---|---|---|---|
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | 720 ≥ 26 | |
| ✅ | docker_containers_memory | memory_usage | 10/10 | 242.67MiB ≤ 370MiB | |
| ✅ | docker_containers_memory | simple_check_run | 10/10 | 596 ≥ 26 | |
| ✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | 0.16GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_0ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | 0.20GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_1000ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | 0.17GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_100ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | 0.18GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_500ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | quality_gate_idle | intake_connections | 10/10 | 3 ≤ 4 | bounds checks dashboard |
| ✅ | quality_gate_idle | memory_usage | 10/10 | 141.61MiB ≤ 147MiB | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | 3 ≤ 4 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | memory_usage | 10/10 | 473.96MiB ≤ 495MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | 3 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | 173.84MiB ≤ 195MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | missed_bytes | 10/10 | 0B = 0B | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | 357.74 ≤ 2000 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | 4 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 10/10 | 370.77MiB ≤ 430MiB | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | missed_bytes | 10/10 | 0B = 0B | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
renovate
Bot
force-pushed
the
renovate/github.com-datadog-dd-trace-go-contrib-net-http-v2-2.x
branch
from
3645730 to
85e2531
Compare
This comment has been minimized.
This comment has been minimized.
github-actions
Bot
added
long review
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
technically this is just a test program not code that is used, but if you give me a few I'll rebase it anyway |
ajwerner
force-pushed
the
renovate/github.com-datadog-dd-trace-go-contrib-net-http-v2-2.x
branch
2 times, most recently
from
f95d2a9 to
44d1646
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
devflow unqueued this merge request: It did not become mergeable within the expected time |
ajwerner
force-pushed
the
renovate/github.com-datadog-dd-trace-go-contrib-net-http-v2-2.x
branch
from
44d1646 to
59e46e3
Compare
ajwerner
force-pushed
the
renovate/github.com-datadog-dd-trace-go-contrib-net-http-v2-2.x
branch
from
59e46e3 to
87fc676
Compare
ajwerner
force-pushed
the
renovate/github.com-datadog-dd-trace-go-contrib-net-http-v2-2.x
branch
from
87fc676 to
bdb8efa
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
gh-worker-dd-mergequeue-cf854d
Bot
deleted the
renovate/github.com-datadog-dd-trace-go-contrib-net-http-v2-2.x
branch
2 participants
This PR contains the following updates:
v2.0.1→v2.2.3Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
DataDog/dd-trace-go (github.com/DataDog/dd-trace-go/contrib/net/http/v2)
v2.2.3Compare Source
What's Changed
This patch release fixes a significant bug that caused dropped spans due to local sampling rules overriding the sampling decision already present in inbound distributed trace context.
Application Performance Monitoring (APM)
Full Changelog: DataDog/dd-trace-go@v2.2.2...v2.2.3
v2.2.2Compare Source
What's Changed
Application Performance Monitoring (APM)
App & API Protection
Profiling
enabledfield to startup log by @mtoffl01 in #3712Ci Visibility
General
@latestto v2fix install command by @mkusaka in #3654New Contributors
Full Changelog: DataDog/dd-trace-go@v2.1.0...v2.2.0
v2.1.0Compare Source
Summary
Application Performance Monitoring (APM)
Client-Side Stats Computation
Client-Side Stats computation is now enabled by default. This feature allows the Go tracer to compute aggregated span statistics locally before sending them to the Datadog Agent, resulting in reduced network traffic and improved performance.
What this means: Instead of sending all raw span data to the Agent, the tracer now sends pre-computed statistics, reducing bandwidth usage while maintaining full observability.
To disable, if needed: Set the environment variable
DD_TRACE_STATS_COMPUTATION_ENABLED=falseor usetracer.WithStatsComputation(false)when starting the tracer programmatically.File-based Configurations
Introduced support for configuring SDK products via a file on the underlying Linux system. #3438 Documentation
Baggage improvements
Fixed a distributed tracing bug in the baggage propagator. Also refactored baggage injection and extraction logic for improved performance and readability. #3439 #3597
Application Security Management (ASM)
contrib envoyproxy/go-control-plane:
What's Changed
Application Performance Monitoring (APM)
Application Security Management (ASM)
Profiling
CI Visibility
General
otelhttpversion by @darccio in #3551New Contributors
Full Changelog: DataDog/dd-trace-go@v2.0.0...v2.1.0
Configuration
📅 Schedule: (UTC)
* 0-4,22-23 * * 1-5)* * * * 0,6)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.